-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[procrunner] avoid waiting for processes forever #65909
[procrunner] avoid waiting for processes forever #65909
Conversation
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-operations (Team:Operations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
# Conflicts: # packages/kbn-pm/dist/index.js
# Conflicts: # packages/kbn-pm/dist/index.js
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
When we use the proc runner to wait for a process to log a specific line before considering it "started", it will wait until the process exits. Doing that has caused issues on CI where in some cases Kibana never is "ready", so we should apply a timeout that kills the process after some time (rather than relying on Jenkins to destroy the workers after 2 hours).
This adds a default
waitTimeout
forproc.run()
calls that specify await
expressions of 15 minutes. This should give any usage enough time to get started, but can be extended by passing an alternatewaitTimeout
, or settingwaitTimeout: false